feat: pass threadId across schema generation requests for conversatio…#1774
Conversation
…n context Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR enables schema-generation follow-up requests to carry the backend conversation thread ID, preserving AI context across prompts in the database schema editor.
Changes:
- Adds
threadIdto schema generation response typing. - Passes the current thread ID into schema generation requests.
- Stores the returned thread ID for subsequent prompts in the same editor session.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
frontend/src/app/services/table-schema.service.ts |
Extends schema generation API typing and request body to include threadId. |
frontend/src/app/components/edit-database-schema/edit-database-schema.component.ts |
Tracks the active schema conversation thread and reuses it on later submissions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…n context